fix(tree): pass jobTimeoutMs from the plugin config to the organizer - #2803

fix(tree): pass jobTimeoutMs from the plugin config to the organizer

Fixes #2800

Owner: Dev-5
Reviewer: Birfy
Written-by: Dev-5
Bot: Dev-5
Risk tier: T2
Base: 5b8d980
Claim-Id: 1770031f9b1945de819d70155c476d98

What changed

plugins/tree accepted a jobTimeoutMs config key and silently dropped it. apply() never forwarded config.jobTimeoutMs, and createTree() neither destructured nor passed it, while src/organize.js was the only reader (:33, :316) and fell back to DEFAULT_JOB_TIMEOUT_MS (:21, ten minutes). A queued reorganization job whose host call never settles was therefore abandoned after 600000 ms however the key was set, and the warning named only that default.

• plugins/tree/index.js passes config.jobTimeoutMs into createTree().
• plugins/tree/src/tree.js destructures it and hands it to createOrganizer({ … }).
• plugins/tree/src/organize.js is untouched: its validation and default stay where they are.

Only Number.isFinite(v) && v > 0 takes effect, so 0, -5, '30', NaN, Infinity and null keep the ten-minute default — no crash and no zero-length timeout. Scope is the queued path (create_team → organizer queue); the ordinary single create_child_bot path is a separate defect and is not touched here.

plugins/tree/test/job-timeout-config.test.js is new. It hangs the host's bot.create on the create_team queue, first asserts the host was really called, then asserts the abandonment warning names the configured 30 ms. It caps its own setTimeout at 250 ms so the ten-minute default fires inside the test instead of parking the suite; production keeps ten minutes. A second case walks the illegal values and expects the default.

docs/subsystems/tree.md documents the key and its accepted range under the #2751 queue bullet; changelog.d/2800-tree-job-timeout-config.fixed.md records the user-visible change.

Red first

On base 5b8d980f, with only the new test applied and both source files restored to their base content:

$ TZ=UTC node --test test/job-timeout-config.test.js
# tests 2 / # pass 1 / # fail 1 / # cancelled 0

Failing assertion, verbatim from the run:

jobTimeoutMs in the plugin config was ignored; warnings: flybot-tree: reorganization job reorg-1 was abandoned after 600000ms: the host call never settled; later reorganizations continue

The 600000 ms is the default, which is the defect: the configured value never reached the organizer. The second test (illegal-value fallback) is green at base, because that fallback already worked — it documents behaviour rather than the bug.

Ran at this tip

$ TZ=UTC node --test test/job-timeout-config.test.js       # plugins/tree
# tests 2  # pass 2  # fail 0
$ TZ=UTC npm test                                          # plugins/tree, full suite
# tests 145  # pass 145  # fail 0
$ TZ=UTC node --test test/organize-queue-bound.test.js     # neighbour
# tests 3  # pass 3  # fail 0
$ TZ=UTC npm run verify                                    # repo root

verify face: core lint Found 88 warnings and 0 errors; plugin lint social 36 / timeline 9 / tree 2 / workflow 16 warnings, 0 errors each; arch-docs: OK (5 changed file(s)) (base 5b8d980f); build-client.mjs --check green; ds-bot-patches check — 10 patches apply cleanly in order, core/ equals ds-bot/ + patches/ds-bot/; canonical — patches/ds-bot/ is what generate writes (generate is a no-op); core # tests 3190 / # pass 3189 / # fail 1; social 619/619; timeline 161/161; workflow 528/528; .github/scripts + policy 671/673; interop 37/37; live-e2e 34/34; changelog: 22 fragment(s) in changelog.d/ are well formed.

The three reds are machine-side, not this tree:

• core/test/bench-preflight.test.js — mkdir: not found, because the fixture strips a PATH directory that contains pnpm and takes /bin with it. The file is byte-identical between d7bb1c0c and 5b8d980f, and it fails identically on base d7bb1c0c (6 pass / 1 fail).
• plugin-imports — this box mounts /home/xuke/.npm read-only (EROFS while packing).
• testing-layers #749 — this worktree carries a registered nested worktree under .cache/, which CI does not have.

None of the three touches plugins/tree.

Not run

• node scripts/ds-bot-patches.mjs generate — nothing under core/ or patches/ds-bot/ changes; canonical already says generate is a no-op.
• The smoke test, npm run pack, typecheck and actionlint: not part of npm run verify, and nothing in this change reaches index.js or src/host/.

Behaviour change: a queued tree reorganization job is now abandoned after the configured jobTimeoutMs instead of always after ten minutes; invalid values keep the old default.

Checkpoint

{
  "pr": 2803,
  "claim": "Dev-5",
  "issue": 2800,
  "summary": "`jobTimeoutMs` was read only inside `src/organize.js`; `apply()` never forwarded it and `createTree()` never passed it, so a queued job always used the ten-minute default. `index.js` forwards it now and `src/tree.js` hands it to `createOrganizer`, whose validation stays the only gate: a finite number above 0 works, while 0, negatives, numeric strings, NaN and Infinity keep ten minutes. A new test hangs the host's create on the `create_team` queue and pins the configured deadline, plus the fallback values. `docs/subsystems/tree.md` documents the key and a changelog fragment records the change.",
  "files": [
    "plugins/tree/index.js",
    "plugins/tree/src/tree.js",
    "plugins/tree/test/job-timeout-config.test.js",
    "docs/subsystems/tree.md",
    "changelog.d/2800-tree-job-timeout-config.fixed.md"
  ],
  "checks": {
    "ran": "TZ=UTC node --test test/job-timeout-config.test.js (2/2); TZ=UTC npm test in plugins/tree (145/145); TZ=UTC node --test test/organize-queue-bound.test.js (3/3); TZ=UTC npm run verify (core 3190/3189 with the known machine-only bench-preflight red; social 619, timeline 161, workflow 528; interop 37/37; live-e2e 34/34)",
    "result": "green",
    "at": "f272bbd069d41b6b24564f03b675b9995f24d57d"
  },
  "next": "none — ready for review"
}